Software in 30 Days by Ken Schwaber & Jeff Sutherland

Author:Ken Schwaber & Jeff Sutherland
Language: eng
Format: epub
Publisher: Wiley
Published: 2012-03-19T04:00:00+00:00

“But if you want an easy-to-use, user-friendly program for doing things with video, this is NOT it. There are things I expected it to do, and it didn't. Or I couldn't make it happen.”4

“. . .this software is the notoriously bad encoder with memory leaks up the wazoo. If you try to encode a large movie file into mpeg2 premiere will more than likely crash on you due to bad memory management. The only solution so far is to simply restart the system and pray it wouldn't happen again.”5

The next release, Premier Pro CS4, was meant to fix CS3's defects. CS4 was to increase the product's ease of use, stability, and speed, as well as halt memory leaks. Peter Green had heard about and decided that short-cycle development would allow Adobe to create complete increments of the total product with every Sprint. The increments would then add up into something that worked and that the customers would love. Peter also wanted to know the real state of affairs every Sprint, so he had several of the teams that were working on CS4 try the Scrum process to see how it worked.

Adobe had over one hundred developers working on 18 Scrum Teams for this release. Everyone figured that integrating all of the increments from all 18 teams each Sprint would be too much work. They decided to wait until near the end of the release to integrate the increments. Just prior to the CS4 release date, the teams tried to integrate their individual pieces of software into one, integrated product. All the discrepancies and unresolved dependencies that precluded integration showed up as bugs and pieces of CS4 not working together. Figure 7.10 shows the slow increase in defects during the development prior to the attempted integration, and then the rapid spike in the number of defects. The developers heroically corrected as many as they could but still had to release the product late with harmful defects. The names of the developers who were hospitalized due to stress and overwork at Adobe are legend.

Figure 7.10 Defects in Adobe CS4 and CS5

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.